Implements #629 - Port-Specific Custom VLAN Tag #630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[NF] New feature summary - closes #629
Adds a customVlanTag parameter to the vlanInterface model and plumbs that through to the UI. This allows a member to have a Peering VLAN handed off on a virtualInterface with a customer port-specific tag. This has also been implemented with the provisioning flow to add a customVlanTag field to the generated YAML file.
I've also included a migration that works against previous versions of the installation.
In addition to the above, I have:
<?= $t->ee( $data ) ?>
or equivalent.